-
Notifications
You must be signed in to change notification settings - Fork 912
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEA] Add an environment variable to fail on fallback in cudf.pandas
#16562
[FEA] Add an environment variable to fail on fallback in cudf.pandas
#16562
Conversation
cudf.pandas
cudf.pandas
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For the reviewer: I can add some more tests, but I wanted to get some feedback on the approach.
/ok to test |
Should the PR title be edited to say that this adds an environment variable instead of a decorator to warn on fallback? Also, do we intend for this environment variable to be publicly usable? If we, we should probably add it in the docs somewhere |
cudf.pandas
cudf.pandas
/ok to test |
d37f525
to
84d7110
Compare
/ok to test |
/ok to test |
For the reviewer: CI takes a while, so I'd prefer a review before I address the merge conflict. |
|
||
@pytest.fixture(autouse=True) | ||
def fail_on_fallback(monkeypatch): | ||
monkeypatch.setenv("CUDF_PANDAS_FAIL_ON_FALLBACK", "True") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will this have to be unset and is the scope of the fixture guaranteed to be limited to this file when ran with pytest-xdist with worksteal
algo?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
According to the pytest docs, the default scope for the fixture is at the function level. So I think each test gets the environment variable set and unset on startup and teardown, respectively.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, it doesn't look like we don't run worksteal
for the cudf.pandas test suite. Should we?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yup, can you add that as part of this pr
/ok to test |
I'm looking into why CI failed. It may have been do to adding
to the pytest command for cudf.pandas tests. |
I'll add this back in a follow-up PR. |
/merge |
Description
This PR makes more on #14975 by adding an environment variable that fails when fallback occurs in cudf.pandas. It also adds some tests that do not fallback.
Checklist